Conversation
bendbennett
left a comment
There was a problem hiding this comment.
Looks good!
Left a comment but I'm not sure it's a significant concern.
I've only reviewed genericvalidator package as you mentioned.
70ac46e to
00d6c85
Compare
bendbennett
left a comment
There was a problem hiding this comment.
LGTM. Couple of minor comments but nothing blocking. Guess the only question I have is around naming of the internal pkg, for instance are we going to use primitivevalidator and collectionvalidator, complexvalidator etc.
|
About the For the collections, I don't have a better name 🤷 , so I'd go for something like |
The underlying implementation sits in `primitivevalidator` package.
9dff486 to
2fc01f4
Compare
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Closes #7
Closes #8
Closes #9
Validators added here, per package:
int64validatorOneOf(int64...),NoneOf(int64...)float64validatorOneOf(float64...),NoneOf(float64...)numbervalidatorOneOf(*big.Float...),NoneOf(*big.Float...)stringvalidatorOneOf(bool, float64...),NoneOf(bool, float64...)boolparameter is to enable/disable case sensitivityThe validators are designed to restrict use to the primitive types, and it will throw errors if used against any collection type.
Implementation for all but the
stringvalidatorpackage is provided by theprimitivevalidatorpackage, that holds the bulk of the logic.